Repository navigation
Separate out travis tests, one per different component to test. - #6220
Conversation
d08b21b to
68f0160
Compare
68f0160 to
96e962f
Compare
…nning and if it's necessary to test at all, given what files are changed
66b1671 to
d4cfeb0
Compare
|
As you can see, there will now be 6 distinct builds for each PR: https://travis-ci.org/EFForg/https-everywhere/builds/151690169 I've added one additional test for the The I expect this will make travis builds faster, since all the tests can run in parallel now. It will also not run tests which are unnecessary for the type of PR (ruleset or core code). Finally, for ruleset maintainers and core maintainers alike, it will now be a little clearer on the travis build page what component of the build is failing, without having to dig into the build logs. |
|
@J0WI just tagging you so you're aware how the breakdown of travis tests will soon look. |
|
|
||
| RULETESTFOLDER="test/rules" | ||
|
|
||
| # Make a list of all changed rulesets, but exclude those |
There was a problem hiding this comment.
This comment is out of date; we're no longer making this list here.
|
Ready for review again! |
|
lgtm |
|
Merge when ready. |
No description provided.